Oh... I've used some PHP 7 specific functions... Too soon to require PHP7?

This PR solves #36, #38 and #39.

@thomasjsn sorry for the delay I've been on a personal matter that needs to be addressed. I will review/test it in the weekend

@ErickTamayo I've made a IsElasticSearchable interface, which I use when iterating models. Want me to add it? Doesn't really require any testing anyways.

@thomasjsn sure you can include it, I'm planning to review this today and think of new features that we can add to it.

@ErickTamayo Sure, I'll add it this evening.

This PR is really VERY huge improvement. Currently working with it.
But for example I search for tag:
"hello", some items get high scoring, all of them, but scoring is:
9.98
9.97 and so on...

But what if I want only those with 'hello' keyword - and order by 'created_at' field.

and this high scoring is not of a big help... that's main issue why I would like to 'disable' default sorting.

thanks for ideas

@huglester What I do is map tags as an array of text or keywords. The I search in that field only: tags:hello. Then the scoring will be the same for all documents that has "hello" in the tags array. And then order by the orderBy attribute.

Hello @thomasjsn and thanks for letting know.

so my initial example was:

'sort' => [
                    [
                        'created_at' => [
                            'order' => 'desc',
                        ],
                        'id' => [
                            'order' => 'desc',
                        ],
                    ],
                ],
                'query' => [
                    'bool' => [
                        'must' => [
                            'term' => ['uri' => $query],
                        ],
                    ],
                ],

so basicly sort part is solved now?

But I am not sure on how to search the tag now?
I mean trying along these lines:

$articles = \Webas\ProfilesModule\Entities\Profile::elasticSearch('multi_match', 'uri:Some-Url', [
            'fields' => ['uri'],
        ])->get();

But I also need BOOL must stuff

Thank you

I often just do a query_string search with field:query. That is the default, unless you have modified the config.

Project::search('tags:mytag`)->orderBy->('created_at')->get();

You can not include the field: in a multi_match search. That only works with query_string.

So either query_string with the search phrase tags:something or multi_match with search phrase something and set the fields property, as you have done.

It helps to familiarize oneself a bit with the different search methods that ElasticSearch provides.

ElasticSearch is extremely configurable, so it's a bit tricky to write a search method that will suit all needs. You can quite easily write your own trait to tailor the search method exactly like you want. Like I have done for counting, see #42. The you can define the search, filters, ordering and everything like you want it. You will need to dig a bit into mapping the returned ids to the eloquent model.

I see @thomasjsn
Thanks again, I think I managed to solve this. There were some indices generated incorrectly which were causing different problems.

Thank you this 42 example. It's good to be able to pass custom queries like so!

What can we do, to merge this PR in origin package?

if that matters, I am currently playing this @thomasjsn fork - and not met any problems. VERY HAPPY :)

I've been using it on my production site for about 2 weeks now ☺️

I am not using in production. but for around a week in development. and very happy user!

Anyone interested, feel free to make the requested changes. For my own need I will be focusing more on Elastic Search specific methods, and less on compliance with searching through Scout.

I must agree with @thomasjsn

Probably some improvements could be made. But the problem with scout is that it is bound to Algolia. you can control lot of stuff in algolia web interface and so on.

Elasticsearch is different. There are different versions etc, since this is separate package, I think it can give some improvements over original Scout. And if separe Trait is used, I do not see any harm.

Sometimes making tool to 'agnotic' you loose 80% of funtionality and you are left with the 'basics':
like lets search for "dog" in the index and return results.

But who uses elasticsearch, probably has more needs than basic search, and needs more control over search.

thank you

@thomasjsn
Can you please open issues tracker in yours fork?
maybe, i just dont wanna flude in main repository

i have couple of ideas to improve, and questions.

at this moment, origin method toSearchableArray() overrides ES mappings in yours mappings() method, while reindexing all. is it ok?
I'm still dealing with the correct configuration of the model.

although i found, that Scout+ES is incompatible with Eloquent\Model::toArray() method, because if we are store model with it relations in ES, method toArray() anyway reloading model relations from DB. I suggest to somehow override toArray method, with excluding already loaded from ES attributes/relations
What do you think?

Discovered, that laravel's method toArray() is not so cool as i expected

@thomasjsn I can't get the search ordering to work, I'm using the following:
$videos = Video::search($query)->orderBy('publishedAt', 'desc')->paginate(5);

Do you know what could cause this?

@reinierkors please open a issue in the fork, this PR is getting bloated with non-related questions about the pr itself.